Deploy preview ready!

Built with commit f10625f

https://deploy-preview-1733--gatsbygram.netlify.com

Deploy preview ready!

Built with commit f10625f

https://deploy-preview-1733--using-drupal.netlify.com

Sweet! Thanks for helping out!

To clean up the diff, run "npm run format" from the base of the repo.

@sebastienfi could you handle reviewing and merging this PR?

Awesome!

@alexbassy

• Could you please update your branch to the latest ? Example on SOF
• Don't need to pass perPage as a parameter because it's already "global" (_perPage)
• Should we keep the default perPage value to 10 or increase it right away to 100 ?
• Can you update the gatbsy-config.js of the example site using-wordpress and test it with the actual configuration ? The request will run against wordpress.com and you will see a lot of errors happening there. You may find this usefull to developp with the example site:

bash #1 : cd gatsby
bash #1 : npm run watch
... and keep it running

bash #2 : cd gatsby/example/using-wordpress
bash #2 : gatsby-dev
... and keep it running

bash #3 : cd gatsby/example/using-wordpress
bash #3 : gatsby-dev --set-path-to-repo ../your-path-to-gatsby-root/
bash #3 : npm i && npm run dev

Will this work for custom post types as well?

@cr101 As of yet, @alexbassy 's implementation will give the per_page querystring parameter to each eandpoint, so it should work. Would you like to clone the topic branch from @alexbassy 's repo and give it a go ?

@sebastienfi Sorry, I'm currently unable to take this for a spin as I'm recovering from a nasty head cold

@sebastienfi thanks for the instructions, I found them very useful. I ran the example using-wordpress my version of the source plugin and it worked fine. The WP example only has 4 posts, so to test the "perPage" param, I set the value to 1, and it requested 4 pages as expected.

• Rebased
• Set default perPage to 100
• Stop passing around perPage
• Use x-wp-totalpages header rather than calculating

👍

One more thing

• Since your modification allows to query every posts no matter the configuration of per_page would be in functions.php, remove the uncessary Readme notice about per_page => Actually I just did the change myself on your branch, you can merge the PR in your topic branch and update your PR in gatsby repo.

@cr101 yes! I just tested it using the "Custom Post Type UI" plugin with these options:

and it worked just fine, the query was allWordpressWpRecipes 👍

@KyleAMathews that's all good for me. I can't merge myself, would you manage it ?

@sebastienfi hmmm lemme look into this.

@sebastienfi you should have merge privileges now.

PLEASE always "Squash and merge". Makes the history much more readable.

Thanks @alexbassy! Making a new release now.

Sweet thanks @KyleAMathews. Is there any list of wanted features for this plugin? I might be working with it a fair bit now, so I'd like to contribute back to the project where I can. One of the things I've done was adding posts to categories as child nodes.

@sebastienfi has been driving this and I know from private conversations has a TODO list for some sites he's working on. You want to make an issue for that Sébastien?

Hiya @alexbassy! 👋

This is definitely late, but on behalf of the entire Gatsby community, I wanted to say thank you for being here.

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (We’ve got t-shirts and hats, plus some socks that are really razzing our berries right now.)
2. If you’re not already part of it, we just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. You’ll receive an email shortly asking you to confirm. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If you have questions, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again! 💪💜